-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Rollup of 11 pull requests #145407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 11 pull requests #145407
Conversation
The tests fail on s390x and presumably other big-endian systems, due to print of raw values and padding bytes. To fix the tests remove the raw output values in the error note with `normalize-stderr`.
When operating on expressions, `cfg_select!` can now handle expressions without braces. (It still requires braces for other things, such as items.) Expand the test coverage and documentation accordingly.
So that it is easier to see which was the last started step when a failure happens on CI.
When verbose mode is enabled, it is very hard to see the actually executed steps.
They could easily get out of sync and miss some fields. Now all steps are instrumented automatically.
Useful for optimizing the sequencing of the compiler's own build.
…nd had no comment
…mpiler-errors cleanup: Remove useless `[T].iter().last()`
Adjust error message grammar to be less awkward r? ``@estebank``
@bors r+ rollup=never p=5 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 898aff704d In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 898aff7 (parent) -> 3507a74 (this PR) Test differencesShow 225 test diffsStage 1
(and 39 additional test diffs) Additionally, 86 doctest diffs were found. These are ignored, as they are noisy. Job group index Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 3507a749b365aae4eefa96ab700a9315d3280ee7 --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Finished benchmarking commit (3507a74): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -3.2%, secondary -0.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.7%, secondary 2.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.4%, secondary 0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 470.516s -> 469.244s (-0.27%) |
Successful merges:
ONLY_HOSTS
in bootstrap #145324 (Rename and documentONLY_HOSTS
in bootstrap)--timings
to cargo #145379 (bootstrap: Support passing--timings
to cargo)rustc-dev-guide
:3 #145397 (Rust documentation, userustc-dev-guide
:3)default_field_values
inResolver
#145398 (Usedefault_field_values
inResolver
)[T].iter().last()
#145401 (cleanup: Remove useless[T].iter().last()
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup